Goal And Delivered Outcome

A message could appear submitted while executor startup showed no reply or progress. The overview receipt also hid activity and turn controls available in the full conversation. This change shows a receipt before session preparation, then observed activity and elapsed time, with cancellation before dispatch and existing exact-turn controls after acceptance.

The shared manager/Goal conversation also preserves upward reading during streaming, provides a return-to-latest action, expands multiline drafts, and removes the suggestion strip from an established conversation. The existing App conversation RFC records the research and observable acceptance boundaries.

Intended base: main. Owner: the existing TypeScript conversation presentation and Chat transport; no new capability, provider, scheduler or backend decision owner.

Scope And Continuation

Complete within this presentation slice. It does not claim to cure provider startup timeouts, implement completion notifications, persist browser elapsed time across restarts, or complete delegated work. CLI/Lark behavior is unchanged because the affected path is the App/browser conversation renderer and session-preparation fetch.

A real read-only goal-wording request succeeded after repairing an installed CLI selection. An earlier live request still timed out before executor turn acknowledgement; sustained startup/recovery remains part of the existing App conversation acceptance, not certified by this UI change.

Validation

• Tested revision: b42dc14d45f086a6b72d13a6193488f034ff10f0
• Run state: finished.
• Input classes: synthetic, public_fixture, authorized_private_read_only.

Initial validation caught and corrected EOF whitespace, missing root TypeScript dependencies and a concurrent-edit guard. CI then exposed stale tests that used a suggestion button to infer turn completion after that button was removed from established conversations. The follow-up observes pending replies directly and opens configuration from the overview; the complete packaged browser suite now passes. The final branch is rebased on main 350f0f3 and removes a duplicate composer height effect. The same startup regression fails on that base and passes on this head. Local architecture replay found two unchanged baseline failures: generated-twin census expects one generated pair but sees two, and the developer book lacks its v1.2.3 release anchor (tracked by #5318). Both fail with the same identity and detail on base and head, outside this presentation path. Merge readiness must resolve these separately; neither failure is hidden or weakened. The prior live Sol result is reused because its executor path is unchanged by the rebase/refinement; a new paid model call was not made. Generated assets and live evidence remain outside Git.

Frontend / Visual Evidence

UI impact: changed. Synthetic screenshots are attached in the conversation: before startup receipt, after overview waiting, desktop conversation and narrow conversation. The before image uses the previously installed release renderer with a synthetic request; after images use the candidate packaged renderer and synthetic SSE.

Attention review: one observed activity line plus elapsed time; details expand on demand. Quiet waiting is explicit, not a fake percentage or changing phase. Controls remain scoped to the actual turn. Drafts grow within 120px, active conversations lose a redundant suggestion strip, and streaming no longer steals the reader's position.

Type of Change

• Bug fix
• Documentation update
• Test update

LoopX Area

• Public docs or presentation surface (dashboard)

Boundary Checklist

• No private state, credentials, raw traces, internal links or machine paths in the diff or public evidence.
• Shared-authority fixture impact: N/A; no authority-store or state-migration change.
• Related refactor applied: one shared activity/control component replaces duplicated overview/full-conversation behavior; the backend remains authoritative for accepted-turn effects.
• Every commit has DCO sign-off.